Method and system for muting audio based on a call event

ABSTRACT

A muting system that allows audio of a computing device to be automatically muted when a telephone call is received on a telephone number associated with the computing device is provided. When an incoming call event occurs for that telephone number, the computing device directs a software component to mute the audio. When the muting system subsequently receives a call event indicating that the call has terminated, it may automatically un-mute or resume the software components. The muting system may allow a user to manually specify to un-mute or resume the software components.

CROSS REFERENCE

This application is related to U.S. patent application Ser. No. 11/067,611 entitled “METHOD AND SYSTEM FOR FORWARDING TELEPHONE CALLS BASED ON PRESENCE INFORMATION” and filed concurrently, which is hereby incorporated by reference.

TECHNICAL FIELD

The described technology relates generally to computer systems for handling telephone call events.

BACKGROUND

Real-time conversations between conversation participants via their computer systems are becoming increasingly common. Such real-time conversation requires that the participants be present at their computer systems (e.g., personal digital assistants) and able to respond when a communication is received. A common form of real-time conversation is provided by instant messaging services. An instant messaging service allows participants to send messages and have them received within a second or two by the other participants in the conversation. The receiving participants can then send responsive messages to the other participants in a similar manner. To be effective, a real-time conversation relies on the participants' becoming aware of, reviewing, and responding to received messages very quickly. This quick response is in contrast to conventional electronic mail systems in which the recipients of electronic mail messages respond to messages at their convenience.

When an initiating participant wants to start a real-time conversation, that participant needs to know whether the intended participants are available to respond in real time to a message. If not, then communications via conventional electronic mail, voice mail, or some other mechanism may be more appropriate. For example, if the computers of the intended participants are currently powered off, then a real-time conversation may not be possible. Moreover, if their computers are currently powered on, but the intended participants are away from their computers, a real-time conversation is also not possible. The initiating participant would like to know the availability of the intended participants so that an appropriate decision on the form of communication can be made.

The availability status of an entity such as a computer system or a user associated with that computer system is referred to as “presence information.” Presence information identifies the current “presence state” of the user. Users make their presence information available so that other users can decide how best to communicate with them. For example, the presence information may indicate whether a user is logged on (“online”) with an instant messaging service or is logged off (“offline”). Presence information may also provide more detailed information about the availability of the user. For example, even though a user is online, that user may be away from their computer in a meeting. In such a case, the presence state may indicate “online” and “in a meeting.”

In an instant messaging context, a publishing user (“publisher”) may provide their presence information to a presence server that then provides the presence information to subscribing users (“subscribers”). Thus, a presence server may use a subscriber/publisher model to provide the presence information for the users of the presence service. Whenever the presence information of a user changes, the presence server is notified of the change by that user's computer system and in turn notifies the subscribing users of the change. A subscribing user can then decide whether to initiate an instant messaging conversation based on the presence information of the intended participants. For example, if the presence information indicates that a publishing user is currently in a conference telephone call, then the subscribing user may decide to send an instant message, rather than place a telephone call, to the publishing user. If the subscribing user, however, needs to call and speak with the publishing user, the subscribing user needs to monitor the presence information of the publishing user to know when the call can be placed. When the subscribing user notices that the publishing user's presence information indicates that the telephone conference has been concluded, the subscribing user can then place the telephone call.

Although presence information is available to subscribing computer systems so that decisions can be made about the appropriate form of communication, presence information is not available to devices that cannot or do not subscribe to presence information. For example, when a person wants to place a telephone call, the person may not know the current location of the person to be called because the person is not near a computer system or the person to be called will not allow the calling person to subscribe to their presence information. As a result, the calling person may try calling several different telephone numbers before locating the called person. Although some systems attempt to address the problem of having to call multiple telephone numbers, those systems have various disadvantages. For example, one system allows a person to have a primary telephone number and to forward calls received on the primary telephone number to other secondary telephone numbers. A disadvantage of such a system is that the person needs to manually forward the calls and needs to remember to forward the calls as the person moves from place to place. Another system allows a person to have a primary telephone number and other secondary telephone numbers. When a call is received on the primary telephone number, the system may sequentially call each secondary telephone number until a call is answered or may simultaneously call the secondary telephone numbers. When a user answers one of the simultaneously placed calls, then the system drops the other calls. A disadvantage of the sequential approach is that it may take a while to sequentially call each secondary telephone number and the calling person needs to wait. A disadvantage of the simultaneous approach is that extra telephone lines are needed to place the simultaneous calls.

Computer systems (and other devices) are increasingly being used to render audio. When a telephone call is received at a telephone near the computer system that is rendering audio, it may be difficult (especially when on a speaker phone) for the user to conduct the telephone conversation because of the volume of the audio. A user typically will try to mute the audio before the call is answered. It may, however, be difficult for the user to find the appropriate user interface for muting the audio. Indeed, the calling person may hang up or be directed to voice mail before the called person can mute the audio and answer the call.

It would be desirable to have a mechanism that would allow a telephone call to be automatically forwarded to a telephone where the called person is currently located. Also, it would be desirable to have a mechanism that would help solve the problem of audio being rendered during a telephone call.

SUMMARY

A muting system that allows the audio of a computing device to be automatically muted when a telephone call is received on a telephone number associated with the computing device is provided. The muting system of a computing device subscribes to receive telephone information for the associated telephone number from the telephone system. When a call event occurs for that telephone number, the telephone system notifies the computing device. If the event is an incoming call, then the computing device directs a software component to mute the audio. When the muting system subsequently receives a call event indicating that the call has terminated, it may automatically un-mute or resume the software components. The muting system may allow a user to manually specify to un-mute or resume the software components.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a presence model of presence states in one embodiment.

FIG. 2 is a block diagram that illustrates systems used by the call forwarding system in one embodiment.

FIG. 3 is a block diagram illustrating remote access of a client computer system in one embodiment.

FIG. 4 is a block diagram that illustrates components of the call forwarding system in one embodiment.

FIG. 5 is a flow diagram that illustrates the processing of the subscribe to other client's information component in one embodiment.

FIG. 6 is a flow diagram that illustrates the processing of the receive incoming call event component in one embodiment.

FIG. 7 is a flow diagram that illustrates the processing of the most active component in one embodiment.

FIG. 8 is a flow diagram that illustrates the processing of the receive missed call event component in one embodiment.

FIG. 9 is a display page illustrating the user interface of the muting system in one embodiment.

FIG. 10 is a flow diagram that illustrates the processing of a subscribe to telephone information component in one embodiment.

FIG. 11 is a flow diagram that illustrates the processing of the receive call event component of the muting system in one embodiment.

FIG. 12 is a flow diagram that illustrates the processing of the receive hang up event component of the muting system in one embodiment.

DETAILED DESCRIPTION

A method and system for automatically forwarding a telephone call to a telephone number based on presence information of a computing device associated with the telephone number is provided. In one embodiment, a call forwarding system forwards telephone calls based on presence information of a user as reported by computing devices associated with telephone numbers. For example, a user may have multiple computing devices such as a workplace desktop, a workplace laptop, a home desktop, a personal digital assistant, and so on. Each computing device may have an associated telephone number (e.g., for a telephone in the office where a desktop is located). The call forwarding system of each computing device subscribes to receive the presence information of each other computing device of the user. The call forwarding system of each computing device also subscribes to receive telephone information (e.g., an incoming call event) from a telephone system for all the telephone numbers associated with the user's computing devices. Each computing device may maintain a list of mappings from the user's computing devices to their associated telephone numbers for subscribing to presence information and telephone information. For example, an office desktop computer of the user may have the telephone number of the telephone in the office or the telephone number of a voice over IP computer-based connection associated with it, and a laptop computer may have the telephone number of a cell phone associated with it. When the telephone system receives an incoming call directed to one of the telephone numbers of the user's computing device, it sends an incoming call event to each computing device. Upon receiving the incoming call event, each computing device determines whether the user is most likely present at that computing device based on the presence information. For example, if it has been 30 seconds since the user last interacted with a computing device and more than two hours since the user last interacted with any of the other computing devices, then the user was most recently active at the computing device with activity 30 seconds ago. When a computing device determines that the user is most likely present at that computing device, it sends a notification to the telephone system to forward the incoming call to the telephone number associated with that computing device. Since each computing device employs the same algorithm and the same presence information for determining whether the user has been most recently active at that computing device, only one computing device will decide to send a call forwarding notification to the telephone system. In this way, a calling person can place a call to any one of the telephone numbers associated with the called person and have the telephone call automatically forwarded to the telephone number associated with the computing device at which the user is most likely present.

In one embodiment, the call forwarding system of the computing device at which the user is most likely present also sends an electronic mail notification to the user indicating that the call has been forwarded. The electronic mail notification may include the name of the calling person, calling telephone number, time of call, called telephone number, forwarded telephone number, and so on. If the telephone call (after being forwarded or not) is not answered, then the computing device that requested the call to be forwarded may send an appropriate electronic mail notification to the user. Alternatively, if all the computing devices receive a call not answered event then a “distinguished” computing device may send the electronic mail notification to the user. A distinguished computing device is the one that can uniquely identify itself based on certain characteristics relative to the other computing devices. For example, the distinguished computing device may have the lowest network address of all the computing devices or may have the most recent user activity. The network addresses may be published with or be derived from the presence information. The call forwarding system may use methods of communication other than electronic mail notifications to notify users. For example, the call forwarding system could provide the notification by sending a text message to a mobile device (e.g., cell phone or pager), sending an instant message, or placing a call to the user on a specified phone number (e.g., a cell phone).

In one embodiment, if the user is not present at any of the computing devices, a distinguished computing device may forward the call to a default telephone number. For example, if each computing device determines that the most recent user activity at any computing device was more than an hour ago, then each computing device may determine that the user is not present at that computing device. The distinguished computing device then requests the telephone system to forward the incoming telephone call to a default telephone number. For example, the default telephone number may be for a cellular phone and/or may provide voice mail services, paging services, and so on. The distinguished computing device may also send an electronic mail message to the user indicating that the call was forwarded to the default telephone number.

The call forwarding system may allow a user to define one or more telephone numbers to be associated with each computing device. The call forwarding system may also rely on automatic association of a telephone number with a computing device. For example, a user may use the laptop that is connected to a wireless LAN via different access points. The call forwarding system may determine the access point through which the laptop is currently accessing the network and automatically associate the laptop with the telephone number of a telephone near that access point. As another example, if the laptop is GPS enabled, then the call forwarding system may use global positioning information to locate a nearby telephone. If the laptop is cell phone enabled, then the call forwarding system may use cell triangulation to locate a nearby telephone.

In one embodiment, the call forwarding system may include a muting system that allows audio of a computing device to be automatically muted when a telephone call is received on a telephone number associated with the computing device. The muting system of a computing device subscribes to receive telephone information for the associated telephone number from the telephone system. When a call event occurs for that telephone number, the telephone system notifies the computing device. If the event is an incoming call, then the computing device may direct the operating system to mute the audio of the computing device. Alternatively, the muting system may direct certain software components (e.g., applications) to mute their audio or to pause. For example, if the software component is playing a movie from a DVD, then the muting system may request the software component to pause the movie. If the software component is receiving a data stream, then it may buffer the data stream while it is paused. When the muting system subsequently receives a hang up event indicating that the call has terminated, it may automatically un-mute or resume the software components. The muting system may allow a user to manually specify to un-mute or resume the software components. In this way, the audio can be automatically muted when a call event occurs.

In one embodiment, the muting system may provide a user interface through which a user can provide configuration information specifying the actions to be taken for the various call events. For example, the user may specify that the audio should be muted when an outgoing call event occurs, but that the software component playing a movie from a DVD should not be paused. Alternatively, the user may specify that the audio should only be muted when an incoming call is answered or an outgoing call is placed using the speakerphone option of the telephone. (The telephone would need to notify the telephone system so that it can notify the computing device.) As another example, the user may specify that the audio should be un-muted when the user selects the mute button of the telephone. The muting system may allow the user to specify on an application-by-application basis to mute or pause the application based on the various call events. The muting system may allow the user to specify that all audio of the computing device should be muted. In that case, the muting system may direct the operating system to mute the audio. The muting system may also allow the muting of audio based on video conferencing events and PSTN conferencing events.

FIG. 1 is a diagram illustrating a presence model of presence states in one embodiment. The presence model 100 defines a hierarchy of presence states of a publishing entity, such as a user, client, or computer system. The first-level presence states 110 are “offline” 111, “online” 112, and “unavailable” 113. “Offline” indicates that the publishing entity is not currently available, “online” indicates that the publishing entity is currently logged on to the presence server, and “unavailable” indicates that no presence information is currently available. The second-level presence states 120 of the “online” presence state are “at home” 121, “at work” 122, and “other” 123. “At home” indicates that the publishing entity is online at home, “at work” indicates that the publishing entity is online at work, and “other” indicates that the publishing entity is online at some other location. The third-level presence states 130 of the “at work” presence state are “in a meeting” 131, “on the phone” 132, and “at lunch” 133, which are self-descriptive. The fourth-level presence states 140 of the “in a meeting” presence state are “in the office” 141 and “out of the office” 142, which are also self-descriptive. A user may be allowed to define the hierarchy of presence states of a presence model and to define multiple presence models. The call forwarding system may allow contacts to define in which presence states they are available to communicate and the method or methods of communication that are allowed or desirable in each presence state. The call forwarding system may also allow a user to select for which presence states of contacts the user wants to be notified.

FIG. 2 is a block diagram that illustrates systems used by the call forwarding system in one embodiment. The call forwarding system is implemented on each client computer system 211-213 and interacts with telephone system 201 and presence system 202 via communications link 203. Each client computer system may have one or more telephone numbers associated with it, such as for telephones 221-223. The telephone system may be a private branch exchange (“PBX”) or some other telephone server (e.g., packet switching, voice over IP) that has a capability to notify the client computer systems when a call event occurs for one of the telephone numbers associated with the client computer systems. The telephone system may allow each client computer system to subscribe to receive the telephone information for various telephone numbers. The presence system allows each client computer system to subscribe to the presence information of each other client computer system. When the presence system receives updated presence information for a client computer system, it notifies the other client computer systems of the update to the presence information of that client computer system. When a client computer system receives an incoming call event from the telephone system, the client computer system determines whether the user was most recently active at that client computer system. If so, the client computer system then directs the telephone system to forward the call to the telephone number associated with that client computer system. For example, when the telephone system receives an incoming call directed to telephone 221, it sends an incoming call event to each client computer system. Each client computer system then determines based on presence information whether the user was most recently active at that client computer system. If client computer system 212 determines that the user was most recently active at that client computer system, then it directs the telephone system to forward the incoming call to telephone 222. Client computer systems 211 and 213 will determine that the user was not most recently active at those computer systems and will not request the telephone system to forward the incoming call.

FIG. 3 is a block diagram illustrating remote access of a client computer system in one embodiment. Client computer systems 302-303 are connected to presence system 301 via communications link 304. The user at client computer system 303 is accessing client computer system 302 remotely. For example, client computer system 303 may be a laptop, and the user is running a certain application on client computer system 302 that is not available on the laptop. Both client computer systems 302-303 published their presence information to the presence system. A difficulty may occur if client computer system 302 detects the user has been most recently active at that computer system. In such a case, the call forwarding system executing on client computer system 302 would direct an incoming call to be forwarded to the telephone number associated with client computer system 302. However, the user may not be physically near client computer system 302. A timing diagram 305 illustrates the difficulty. A user at client computer system 303 may interact with client computer system 303 at time 1:00:00. Client computer system 303 then publishes the activity to the presence system. Because the interaction relates to a remote access, client computer system 303 sends a notification request to client computer system 302. Client computer system 302 receives the request at time 1:00:01 and publishes the activity to the presence system. If an incoming call event is received at time 1:00:02, then client computer systems 302-303 will both determine that client computer system 302 was most recently active. To prevent this determination, each computer system publishes whether an activity is the result of remote access or not. When a client computer system identifies the client computer system whose activity has been most recent, it discards activities indicated as being via remote access. Thus, in the example above, both client computer systems 302-303 will discard the activity of client computer system 302 at time 1:00:01 and determine that the most recent activity was by client computer system 303 at time 1:00:00.

FIG. 4 is a block diagram that illustrates components of the call forwarding system in one embodiment. The call forwarding system 400 includes a subscribe to other client's information component 401, a receive presence event component 402, a receive incoming call event component 403, a receive missed call event component 404, a most active component 405, and a muting system 406. The muting system includes a receive call event component 407 and a receive hang up event component 408. The call forwarding system also includes a presence store 409 and a client store 410. The subscribe to other client's information component subscribes to receive the presence information and telephone information of the other client computer systems and their associated telephone numbers. The client store contains a list of the other client computer systems along with their associated telephone numbers. The receive presence event component receives event notifications from the presence system and stores the presence information in the presence store. The receive incoming call event component is invoked when an incoming call event is received, and it invokes the most active component to determine whether the client computer system is the most active. If it is, then it directs the telephone system to forward the incoming call to an associated telephone number. The received missed call event notification component is invoked when a call not answered event is received. The component determines whether the client computer system is the distinguished client computer system and, if so, sends an electronic mail notification to the user. The receive call event component of the muting system is invoked when a call event occurs and mutes or pauses based on a configuration information. The receive hang up event component is invoked when a call hang up event is received and un-mutes or resumes applications.

The computing device on which the call forwarding system is implemented may include a central processing unit, memory, input devices (e.g., keyboard and pointing devices), output devices (e.g., display devices), and storage devices (e.g., disk drives). The memory and storage devices are computer-readable media that may contain instructions that implement the call forwarding system. In addition, the data structures and message structures may be stored or transmitted via a data transmission medium, such as a signal on a communication link. Various communication links may be used, such as the Internet, a local area network, a wide area network, a point-to-point dial-up connection, a cell phone network, and so on.

Embodiments of the call forwarding system may be implemented in various operating environments that include personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, digital cameras, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and so on. The computer systems may be cell phones, personal digital assistants, smart phones, personal computers, programmable consumer electronics, digital cameras, and so on.

The call forwarding system may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, and so on that perform particular tasks or implement particular abstract data types. Typically, the functionality of the program modules may be combined or distributed as desired in various embodiments.

FIG. 5 is a flow diagram that illustrates the processing of the subscribe to other client's information component in one embodiment. The component subscribes to presence information and telephone information associated with the other client computer systems. In block 501, the component selects the next client computer system from the client store. In decision block 502, if all the client computer systems have already been selected, then the component completes, else the component continues at block 503. In block 503, the component subscribes to the presence information of the selected client computer system. In block 504, the component subscribes to the telephone information of the selected client computer system and then loops to block 501 to select the next client computer system.

FIG. 6 is a flow diagram that illustrates the processing of the receive incoming call event component in one embodiment. The component is invoked when the client computer system receives an incoming call event from the telephone system. In decision block 601, the component invokes the most active component to determine whether the client computer system on which the component is executing is the most active. If the client computer system is the most active, then the component continues at block 602. If none of the client computer systems are currently active, then the component continues at block 604, else the component completes. In block 602, the component notifies the telephone system to forward the incoming call to the telephone number associated with the client computer system. In block 603, the component sends an electronic mail message to the user indicating that the call has been forwarded and the component completes. In decision block 604, if this client computer system is the distinguished client computer system, then the component continues at block 605, else the component completes. In block 605, the component notifies the telephone system to forward the incoming call to the default telephone number. In block 606, the component sends an electronic mail message to the user indicating that the incoming call has been forwarded to the default number. The component then completes.

FIG. 7 is a flow diagram that illustrates the processing of the most active component in one embodiment. The most active component determines whether the user is currently most active at the client computer system on which it is executing. The component returns an indication of true if it is, false if another client computer system is most active, and none if the user is not active at any client computer system. In block 701, the component initializes the last activity variable to the time of the earliest possible activity. In blocks 702-706, the component loops selecting each client computer system and determining whether its last activity is more recent than the last activity encountered so far. In block 702, the component selects the next client computer system. In decision block 703, if all the client computer systems have already been selected, then the component continues at block 707, else the component continues at block 704. In decision block 704, if the last activity (e.g., non-remote activity) of the selected client computer system is more recent than the last activity encountered so far, then the component continues at block 705, else the component loops to block 702 to select the next client computer system. In block 705, the component sets the last activity encountered so far to the last activity of the selected client computer system. In block 706, the component records that the selected client computer system has the most recent activity encountered so far. The component then loops to block 702 to select the next client computer system. In decision block 707, if the last activity of a client computer system is too long ago to consider the user to be active, then the component returns an indication that the user is not active at any client computer system, else the component continues at block 708. In decision block 708, if the client computer system that is executing has been identified as having the most recent user activity, then the component returns true, else the component returns false.

FIG. 8 is a flow diagram that illustrates the processing of the receive missed call event component in one embodiment. The component is invoked when a client computer system receives from the telephone system a call not answered event. In decision block 801, if this client computer system is the distinguished client computer system, then the component sends an electronic mail message to the user indicating that the call was missed in block 802. The component then returns.

FIG. 9 is a display page illustrating the user interface of the muting system in one embodiment. The display page 900 includes an event selection area 901 and action selection area including a mute all checkbox 902, application selection drop-down lists 903, application mute checkboxes 904, and application pause checkboxes 905. A user may specify one or more telephone events in the event selection area and indicate the application and action in the action selection area. For example, the user may select the incoming call checkbox, select an application that renders a DVD from the drop-down list, and select the pause checkbox. After the user has specified the selection, the user may select the submit button 906 to submit the configuration. When an incoming call event is received by the client computer system, it will direct the application that renders a DVD to pause. One skilled in the art will appreciate that additional events (e.g., call answered) and actions (e.g., lower volume) may also be defined and that a different user interface may be used.

FIG. 10 is a flow diagram that illustrates the processing of a subscribe to telephone information component in one embodiment. In block 1001, the component retrieves the telephone number associated with the client computer system. In block 1002, the component sends a subscribe message to the telephone system to subscribe to all call related events directed to the retrieved telephone number. The component then completes.

FIG. 11 is a flow diagram that illustrates the processing of the receive call event component of the muting system in one embodiment. The component retrieves the configuration information for the muting system and configures the applications accordingly. In block 1101, the component retrieves the configuration information for the muting system. In decision block 1102, if the configuration information indicates to mute all audio, then the component continues at block 1103, else the component continues at block 1104. In block 1103, the component notifies the operating system to mute all audio. In blocks 1104-1108, the component loops selecting each application specified in the configuration information and taking the specified action. In block 1104, the component selects the next application of the configuration information. In decision block 1105, if all the applications have already been selected, then the component completes, else the component continues at block 1106. In decision block 1106, if the action associated with the selected application is to pause, then the component continues at block 1107, else the component continues at block 1108. In block 1107, the component notifies the selected application to pause and then loops to block 1104 to select the next application. In block 1108, the component notifies the selected application to mute and then loops to block 1104 to select the next application.

FIG. 12 is a flow diagram that illustrates the processing of the receive hang up event component of the muting system in one embodiment. The component retrieves the configuration information for the muting system and undoes the action performed when the corresponding incoming call event was received. In block 1201, the component retrieves the configuration information for the muting system. In decision block 1202, if the configuration information indicates to mute all audio, then the component continues at block 1203, else the component continues at block 1204. In block 1203, the component notifies the operating system to un-mute all audio. In blocks 1204-1208, the component loops selecting each application specified in the configuration information and undoing the specified action. In block 1204, the component selects the next application of the configuration information. In decision block 1205, if all the applications have already been selected, then the component completes, else the component continues at block 1206. In decision block 1206, if the action associated with the selected application is to pause, then the component continues at block 1207, else the component continues at block 1208. In block 1207, the component notifies the selected application to resume and then loops to block 1204 to select the next application. In block 1208, the component notifies the selected application to un-mute and then loops to block 1204 to select the next application.

From the foregoing, it will be appreciated that specific embodiments of the call forwarding system have been described herein for purposes of illustration, but that various modifications may be made without deviating from the spirit and scope of the invention. One skilled in the art will appreciate that a “telephone call,” as used in this description, encompasses various types of voice conversations (e.g., voice over IP and voice over traditional telephone systems). One skilled in the art will appreciate that a computer system may have multiple telephone numbers associated with it. For example, a computer system may have a telephone number for a voice over IP and for a traditional telephone. In such a case, the call forwarding system may decide to forward the call to one of the telephone numbers based on presence information. For example, if the presence information indicates that the user is hosting a conference call with several people in the same room, then the call forwarding system may forward the call to the voice over IP telephone number to take advantage of the computer's sound system. In one embodiment, the muting system may optionally lower the volume of audio a specified level, rather than muting the audio. In that case, the muting system may record the volume level before it is lowered and restore the volume to that level after the call has completed. In one embodiment, the muting system may gradually decrease the volume when muting and gradually increase the volume when unmuting. The gradual change in volume (e.g., over 1-2 seconds) may be especially important when unmuting to prevent a sudden start to loud music. The muting system may also allow a user to select whether to automatically unmute when a call is completed. Accordingly, the invention is not limited except as by the appended claims. 

1. A method in a computer system for controlling the computer system in response to a telephone event, the method comprising: displaying to a user an indication of telephone events for a telephone number including an incoming call event, an outgoing call event, a call answer event, and a call end event; displaying to the user an indication of applications of the computer system; receiving from the user an indication of a first action to take for a first application of the applications when a first telephone event of a plurality of telephone events for a telephone number is received, the first action including one or more of mute audio of, un-mute audio of, pause, and resume the first application; storing a first indication to take the first action when the first telephone event occurs for the first application; receiving from the user an indication of a second action to take for a second application of the applications when a second telephone event of the plurality of telephone events for the telephone number is received, the second action including one or more of mute audio of, un-mute audio of, pause, and resume the second application; storing a second indication to take the second action when the second telephone event occurs for the second application; receiving from the telephone system a notification that a telephone event has occurred for the telephone number; and upon receiving the notification that a telephone event has occurred for the telephone number, when the received notification indicates that the first telephone event has occurred, taking the first action for the first application as indicated by the first indication; and when the received notification indicates that the second telephone event has occurred, taking the second action for the second application as indicated by the second indication so that the user can control the actions to take when different telephone events occur on an application-by-application basis.
 2. The method of claim 1 wherein upon receiving an indication from the user to un-mute the audio, directing the application to un-mute the audio.
 3. The method of claim 1 including allowing the user to manually un-mute audio of an application that is currently muted as a result of a telephone event and to manually resume an application that is currently paused as a result of a telephone event.
 4. The method of claim 1 wherein when an application is paused, it buffers data being streamed to the computer system during the pause.
 5. The method of claim 1 wherein the first application is the same as the second application, the first telephone event is different from the second telephone event, and the first action is different from the second action.
 6. The method of claim 1 wherein the first application is different from the second application, the first telephone event is the same as the second telephone event, and the first action is the same as the second action.
 7. A computer-readable storage medium containing instructions for controlling a computer system to control software components in response to a telephone event, by a method comprising: displaying to a user an indication of telephone events that include an incoming call event, an outgoing call event, a call answer event, and a call end event; displaying to the user an indication of software components of the computer system; receiving from the user an indication of actions to take for software components when a telephone event is received, the actions selected from the group comprising mute audio of, un-mute audio of, pause, and resume the software component; for each action, storing an indication to take that action when a telephone event occurs for a software component; receiving a notification that a telephone event has occurred; and upon receiving the notification that a telephone event has occurred, for each stored indication of an action to take for a software component when that telephone event occurs, directing the software component to perform the indicated action so that the user can control the actions to take when different telephone events occur on an component-by-component basis.
 8. The computer-readable storage medium of claim 7 including receiving from a user configuration information for muting.
 9. The computer-readable storage medium of claim 7 wherein a software component is outputting both audio and video and the computer readable-storage medium including directing the software component to mute the audio so that the video continues to be output by the software program when a telephone event occurs.
 10. The computer-readable storage medium of claim 7 wherein when a software component is paused as a result of an action being taken when a telephone event occurs, it buffers data being streamed to the software component during the pause.
 11. A system with a processor and memory for controlling a computer system to control a software component in response to telephone event, comprising: means for displaying to a user an indication of telephone events that include an incoming call event, an outgoing call event, a call answer event, and a call end event; means for displaying to the user an indication of software components of the computer system; means for receiving from the user an indication of an action to take for a software component when a telephone event for a telephone number is received, the actions including mute audio, un-mute audio, pause, and resume of the software component; means for storing an indication of the action to take for the software component when that telephone event occurs for each of a plurality of telephone events; means for subscribing to receive telephone events from a telephone system for the telephone number; means for receiving from the telephone system a notification that a telephone event has occurred for that telephone number; and means for directing the software component to, upon receiving the notification, for each stored indication of an action to take for a software component when that telephone event occurs, to perform the indicated action so that the user can control the actions to take when different telephone events occur on a component-by-component basis. 